The spinservers command node includes the following commands:
createcluster
joincluster
modify
reboot
sendsupportinfo
show
shutdown
Each of the commands is described in detail, with parameters and arguments listed for each command. Examples of command usage are included in the discussions.
Note: You enter the SpinServer ID is entered into the system when you initially install the SpinFS software. The name of the SpinServer is propagated from that initial installation into the management framework. To prevent confusion and potential loss or misplacement of data, the SpinServer IDs you choose must be orderly and easily recognizable by all system administrators who maintain your SpinServer system. Any naming system can be chosen for your system, but the IDs for the SpinServers must be unique within a cluster. After the ID for a SpinServer is set, you cannot modify the server name or host name. To do so invalidates the failover port designation for the SpinServer and can result in the loss of data.
Note: The cluster port must be configured even if only a single SpinServer is being installed to assure that all system components work together properly. Even if you intend to use only one of the cluster ports, it is highly recommended that you configure both cluster ports at initial installation of the software.
CLI:
spinservers createcluster -ssid spinserver -clustername cluster_name -ipaddress1 IP_address [-ipaddress2 IP_address] -netmask1 netmask [-netmask2 netmask] [-broadcast1 IP_address] [-broadcast2 IP_address] [-mtu1 maximum_transmission_unit] [-mtu2 maximum_transmission_unit]
GUI: Navigate to the SpinServers node, then select a server from the table and run the Create Cluster command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed, then click Create Cluster.
The spinservers createcluster command creates a cluster with one SpinServer.
Important: This command must not be used for any other purpose. If you mistakenly execute the spinservers createcluster command instead of the spinservers joincluster command, you must reinstall the SpinServer (or completely delete all configuration data) to undo the operation.
-ssid spinserver
This is the ID given to the SpinServer.
-clustername cluster_name
This is the name given to the cluster.
-ipaddress1 IP_address
This is the IP address of the first cluster interface.
[-ipaddress2 IP_address]
This is the IP address of the second cluster interface.
-netmask1 netmask
This is the primary netmask of the cluster network.
[-netmask2 netmask]
This is the secondary netmask of the cluster network.
[-broadcast1 IP_address]
This is the primary broadcast IP address. It is automatically displayed by the SpinServer system.
[-broadcast2 IP_address]
This is the secondary broadcast IP address.
[-mtu1 maximum_transmission_unit]
This is the maximum transmission unit setting for the server's primary network port, specified in bytes. The default is 1500.
[-mtu2 maximum_transmission_unit]
This is the maximum transmission unit setting for the server's secondary network port, specified in bytes. The default is 1500.
The following command example creates a cluster with one SpinServer named Server1. The cluster name is set to Cluster1. The IP address of the first cluster interface is set to 192.168.0.0, and the IP address of the second cluster interface is set to 192.168.0.1. The netmask of the cluster network is set to 255.255.0.0. The broadcast IP address is set to 192.168.255.255. The MTU setting is 9000 bytes.
spinserver::> spinservers createcluster -ssid Server1 -clustername Cluster1 -ipaddress1 192.168.0.0 -ipaddress2 192.168.0.1 -netmask1 255.255.0.0 -broadcast1 192.168.255.255 -mtu1 9000
CLI:
spinservers joincluster -ssid spinserver -clusternodeipaddress IP_address -ipaddress1 IP_address [-ipaddress2 IP_address] -netmask1 netmask [-netmask2 netmask] [-broadcast1 IP_address] [-broadcast2 IP_address] [-mtu1 maximum_transmission_unit] [-mtu2 maximum_transmission_unit]
GUI: Navigate to the SpinServers node, then select a server from the table and run the Join Cluster command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed, then click Join Cluster.
-ssid spinserver
This is the ID given to the SpinServer.
-clusternodeipaddress IP_address
This is the cluster IP address of a SpinServer already in the cluster that you want another SpinServer to join. The SpinServer already in the cluster must be healthy and in active communication with the cluster. It can be any healthy host within the cluster.
-ipaddress1 IP_address
This is the IP address of the first cluster interface.
[-ipaddress2 IP_address]
This is the IP address of the second cluster interface.
-netmask1 netmask
This is the primary netmask of the cluster network.
[-netmask2 netmask]
This is the secondary netmask of the cluster network.
[-broadcast1 IP_address]
This is the primary broadcast IP address.
[-broadcast2 IP_address]
This is the secondary broadcast IP address.
[-mtu1 maximum_transmission_unit]
This is the maximum transmission unit setting for the server's primary network port, specified in bytes. The default is 1500.
[-mtu2 maximum_transmission_unit]
This is the maximum transmission unit setting for the server's secondary network port, specified in bytes. The default is 1500.
The following command example adds a SpinServer named Server2 to a cluster. The IP address of the cluster host is 192.168.0.10. The IP address of the first cluster interface is 192.168.0.0, and the IP address of the second cluster interface is 192.168.0.1. The netmask is 255.255.0.0. The broadcast IP address is 192.168.255.255. The MTU setting is 4400 bytes.
spinserver::> spinserver joincluster -ssid Server2 -clusternodeipaddress 192.168.0.10 -ipaddress1 192.168.0.0 -ipaddress2 192.168.0.1 -netmask1 255.255.0.0 -broadcast1 192.168.255.255 -mtu1 4400
CLI:
spinservers modify -ssid spinserver [-ownername owner_name] [-contact contact_information] [-assettag asset_tag] [-systime system_time] [-tz time_zone]
GUI: Navigate to the SpinServers node, then select the appropriate server from the table and run the Show command from the drop-down menu of the action pane. Make the appropriate modifications in the table that is displayed, then click Modify.
The spinservers modify command changes the owner name, contact information, system time, and time zone for the specified SpinServer.
-ssid spinserver
This is the ID given to the SpinServer.
[-ownername owner_name]
This is the name of the organization, department, or person who creates, is responsible for the maintenance of, or exercises administrative control over the SpinServer.
[-contact contact_information]
This is the information needed to contact the person, organization, or department that is named as the owner of the SpinServer.
[-assettag asset_tag]
This is the asset tag of the SpinServer.
[-systime system_time]
This specifies the SpinServer's current time setting. It is specified in the form YYYY/MM/DD HH:MM:SS, with all zeroes included.
[-tz time_zone]
This specifies the time zone in which the SpinServer is located.
The following command example changes the SpinServer contact information for a server named Server1. The owner is listed as acmebricks, and the contact information is listed as engineering@acmebricks.com. The system time is set to 1:30 p.m. on 1 June 2003.
spinserver::> spinservers modify -ssid Server1 -ownername acmebricks -contactengineering@acmebricks.com -systime 2003/06/01 13:30:00
CLI:
spinservers reboot -ssid spinserver -rebootreason reason_for_restart
GUI: Navigate to the SpinServers node, then select a server from the table and run the Reboot SpinServer command from the drop-down menu of the action pane.
The spinservers reboot command restarts a SpinServer. After you issue the command, you are prompted for confirmation before the SpinServer restarts. Before restarting the SpinServer, the command saves support data to assist with possible troubleshooting.
-ssid spinserver
This is the ID given to the SpinServer.
-rebootreason reason_for_restart
This is the reason for restarting the SpinServer. The reason is written to the event log and is displayed in the subsequent startup message.
The following command example restarts a SpinServer named Server0 and lists a reason of 'SpinFS upgrade'.
spinserver::> spinservers reboot -ssid Server0 -rebootreason 'SpinFS upgrade'
CLI:
spinservers sendsupportinfo -ssid spinserver -type {email | ftp} -parameters parameters
GUI: Navigate to the SpinServers node, then select a server from the table and run the Send Support Info command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed, then click Send Support Info.
The spinservers sendsupportinfo command sends support information about a SpinServer to Network Appliance Technical Support. Use this command at the direction of Technical Support personnel.
-ssid spinserver
This is the ID given to the SpinServer from which support information is to be sent.
-type {email | ftp}
This specifies whether support information is to be sent via email or FTP.
-parameters parameters
This specifies the parameters to be used to send support information. If the value of the -type parameter is specified as email, specify parameters of the form email_server, email_id1, email_id2, etc. If the value of the -type parameter is specified as ftp, specify a parameter of the form FTP_URL.
The following command example sends support information from a SpinServer named Server1 to the FTP URL ftp://ftp.spinnakernet.com/incoming.
spinserver::> spinservers sendsupportinfo -ssid Server1 -type ftp -parameters ftp://ftp.spinnakernet.com/incoming
CLI:
spinservers show [-ssid spinserver]
GUI: Navigate to the SpinServers node. To display information about a specific SpinServer, select it from the table and run the Show command from the drop-down menu of the action pane.
The spinservers show command displays configuration information about all SpinServers if the -ssid parameter is not specified or information about one SpinServer if the parameter is specified. The following information about the SpinServer or SpinServers is displayed:
SpinServer ID
Owner (specific SpinServer only)
Contact information (specific SpinServer only)
Serial number
Asset tag (specific SpinServer only)
Location
System uptime
System time (specific SpinServer only)
Time zone (specific SpinServer only)
The following example displays configuration information for all SpinServers in a cluster.
spinserver::> spinservers show
SpinServer Serial System Uptime Location
ID Number
serv1 1234567890 3 days 12 hr 43 min 15 sec Software Lab
serv2 9876543210 1 day 04 hr 17 min 55 sec Software Lab
CLI:
spinservers shutdown -ssid spinserver -shutdownreason reason_for_shutdown
GUI: Navigate to the SpinServers node, then select a server from the table and run the Shutdown SpinServer command from the drop-down menu of the action pane.
The spinservers shutdown command shuts down a SpinServer. After you issue the command, you are prompted for confirmation before the SpinServer shuts down. The reason for the shutdown is written to the event log and is displayed in the subsequent startup message.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.